Fiber AI

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Discover and call any Fiber AI B2B data API, from company and people search to contact enrichment, through five meta-tools.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Fiber AI": {
      "url": "https://mcp.fiber.ai/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• search_endpoints read-only

  Canonical API selection tool for endpoint discovery and ranking. Use this first to get the top recommended operations for a user intent. Supports optional constraints plus tag-scoped selection via preferredTags, excludedTags, or a curated tagPack key.

  Parameters:

  • query (required) — string
  • limit
  • tagPack
  • constraints
  • excludedTags
  • preferredTags

  Hints: read-only yes · destructive not declared · idempotent yes · open-world yes

• list_tag_packs read-only

  List curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment).

  Hints: read-only yes · destructive not declared · idempotent yes · open-world yes

• list_all_endpoints read-only

  List available Fiber API endpoints with optional tag/search filtering.

  Parameters:

  • tags
  • limit
  • search
  • tagPack

  Hints: read-only yes · destructive not declared · idempotent yes · open-world yes

• get_endpoint_details_full read-only

  Get COMPLETE schema and details for a specific API operation. Use this BEFORE calling an API to understand exactly what parameters are needed. Args: operationId: The operation ID (e.g., "syncContactEnrichment") Returns: Complete schema including all required/optional fields, request body schema, response schema, and example usage.

  Parameters:

  • operationId (required) — string

  Hints: read-only yes · destructive not declared · idempotent yes · open-world yes

• call_operation

  Execute any Fiber API operation by operationId. IMPORTANT: - Most operations require `apiKey` in the request body. - Prefer search_endpoints() first when operation choice is ambiguous. - Use get_endpoint_details_full(operationId='...') first for complex/nested parameter shapes. Args: operationId: The operation ID to call params: Parameters dict: {"body": {...}, "path": {...}, "query": {...}} Returns: API response data or error details.

  Parameters:

  • operationId (required) — string
  • params

  Hints: read-only no · destructive no · idempotent no · open-world yes

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.